FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource Requirements/FHIR Server from package hl7.ehrs.ehrsfmr21#current (15 ms)

Package hl7.ehrs.ehrsfmr21
Type Requirements
Id Id
FHIR Version R5
Source http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.6.4.html
Url http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.6.4
Version 2.1.0
Status active
Date 2024-11-26T16:30:50+00:00
Name AS_6_4_Support_Triage_Categorization
Title AS.6.4 Support Triage Categorization (Function)
Experimental False
Realm uv
Authority hl7
Description Provide support for prioritizing patients based upon acuity, wait time, and practitioner load.
Purpose An EHR-S should support the management of patients waiting for care by displaying them and supporting decisions by the clinicians who are caring for them. The triage process not only collects data on arriving patients, but the categorization and prioritization of patients who are unable to be seen immediately. It is a dynamic process where patient priorities change over time. Unless a care team has unlimited resources, some patients will invariably need to wait.

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Statement N:

Provide support for prioritizing patients based upon acuity, wait time, and practitioner load.

Description I:

An EHR-S should support the management of patients waiting for care by displaying them and supporting decisions by the clinicians who are caring for them. The triage process not only collects data on arriving patients, but the categorization and prioritization of patients who are unable to be seen immediately. It is a dynamic process where patient priorities change over time. Unless a care team has unlimited resources, some patients will invariably need to wait.

Criteria N:
AS.6.4#01 SHALL

The system SHALL provide the ability to manage a triage acuity rating for a patient.

AS.6.4#02 SHALL

The system SHALL capture, maintain and render triage acuity ratings derived from standardized acuity scales.

AS.6.4#03 dependent MAY

The system MAY provide the ability to capture and maintain configurable triage acuity ratings according to scope of practice, organizational policy, and/or jurisdictional law.

AS.6.4#04 MAY

The system MAY present evidence based triage business rules algorithms during the triage process.

AS.6.4#05 MAY

The system MAY capture and update a triage assignment in response to specific prompts for patient associated data or data already captured in the record (e.g., arrival by ambulance, age, vital signs).


Source

{
  "resourceType" : "Requirements",
  "id" : "EHRSFMR2.1-AS.6.4",
  "meta" : {
    "profile" : [
      "http://hl7.org/ehrs/StructureDefinition/FMFunction"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Provide support for prioritizing patients based upon acuity, wait time, and practitioner load.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>An EHR-S should support the management of patients waiting for care by displaying them and supporting decisions by the clinicians who are caring for them. The triage process not only collects data on arriving patients, but the categorization and prioritization of patients who are unable to be seen immediately. It is a dynamic process where patient priorities change over time. Unless a care team has unlimited resources, some patients will invariably need to wait.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.6.4#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage a triage acuity rating for a patient.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.6.4#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL capture, maintain and render triage acuity ratings derived from standardized acuity scales.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.6.4#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture and maintain configurable triage acuity ratings according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.6.4#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY present evidence based triage business rules algorithms during the triage process.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.6.4#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY capture and update a triage assignment in response to specific prompts for patient associated data or data already captured in the record (e.g., arrival by ambulance, age, vital signs).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
  },
  "url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.6.4",
  "version" : "2.1.0",
  "name" : "AS_6_4_Support_Triage_Categorization",
  "title" : "AS.6.4 Support Triage Categorization (Function)",
  "status" : "active",
  "date" : "2024-11-26T16:30:50+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "Provide support for prioritizing patients based upon acuity, wait time, and practitioner load.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001",
          "display" : "World"
        }
      ]
    }
  ],
  "purpose" : "An EHR-S should support the management of patients waiting for care by displaying them and supporting decisions by the clinicians who are caring for them. The triage process not only collects data on arriving patients, but the categorization and prioritization of patients who are unable to be seen immediately. It is a dynamic process where patient priorities change over time. Unless a care team has unlimited resources, some patients will invariably need to wait.",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-AS.6.4-01",
      "label" : "AS.6.4#01",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to manage a triage acuity rating for a patient."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-AS.6.4-02",
      "label" : "AS.6.4#02",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL capture, maintain and render triage acuity ratings derived from standardized acuity scales."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-AS.6.4-03",
      "label" : "AS.6.4#03",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY provide the ability to capture and maintain configurable triage acuity ratings according to scope of practice, organizational policy, and/or jurisdictional law."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-AS.6.4-04",
      "label" : "AS.6.4#04",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY present evidence based triage business rules algorithms during the triage process."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-AS.6.4-05",
      "label" : "AS.6.4#05",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY capture and update a triage assignment in response to specific prompts for patient associated data or data already captured in the record (e.g., arrival by ambulance, age, vital signs)."
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.